Generate IDOC through error

Hello,
I have to create an Idoc that be started when happens some message error in creating of QM process (for example)
How can I start an Idoc in this case?
Anybody can help me, please?
Tku

Hello,
I guess a custom solution would be required,
You will have to capture the event when a error is triggered and code the logic to process an IDOC for the same.
Regards,
Abhishek

Similar Messages

ALE Error while sending PO IDOC through EDI

Hi Experts,
                  I am sending one PO IDOC through EDI but I am getting the following error:-
                  Message no. B1130.
                  "Too many recipients found for message type ORDERS in the ALE model"
                  How can I solve this error ? Please guide me in this regards as this is an
                  important issue with urgency.
Thanks & Regards
Jitendra Gujarathi

Please check this discussion thread
Re: Too many recipients found for message type in the ALE model

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
Reward points if useful and close thread if resolved

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

Error generating IDOC (Transaction F110) - Segment E1IDIBA is blank

Hi experts,
I'm facing a problem here when trying to generate an IDOC through F110.
I'm using PEXR2003 that needs to be sent to a German Bank.
On this IDOC Type (which was never used before on this company) I need the new fields (updated from PEX2002) to be filled up.
The segment that I need the informations to be filled up is E1IDIBA (IBAN and SWIFT-Code).
Does anybody know how I can get this segment filled?
I've been stuck on this point for 2 days!
Thank you very much!

EXIT_SAPLIEDP_902 is the user exit to add/modify segments in PEXR2003 IDoc, if the contents differs for each payment document number processed in the IDoc. This user exit is called at the end of processing for each payment document. We use it in our company for manipulating the PAYEXT IDoc before it is sent to the banks for clearing the payment to our vendors.
To debug this user exit, you need to set and save the parameters and/or payment proposal in F110 but should not actually run it, if you want your breakpoints to be hit.
Put your breakpoint and run the program RFFOEDI1 with the payment run date and identification saved in F110 through SE38.
If the above exit is not what you are looking for there are two other user exits EXIT_SAPLIEDP_901 and EXIT_SAPLIEDP_903, which are called at the beginning and end of processing for each bank (i.e., EDI partner)
Regards,
Vishnu Tallapragada

Generating GR Idoc through Output

Hi,
I will be doing GR in ECC and will send the same to another system through IDOC WMMBID02.
I am thinking of sending the same immediately once GR is done through Output config , I am thinking of using output type We01.
Is there any other modification that we have to do (Programme in the Output / TRansmission Medium etc).
Or is there any other output type i should use.
REgards.
BG

Hi BG,
Was you able to generate IDOC for GR/GI/Transfer posting and update the SAP inventory into external system at run time? I have the same request from client as yours now.
Hope you can give some idea on how the settings done to do this.
Thanks,
Trang

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

IDoc to IDoc through ALE

hello experts !! could u plz give me some idea or step by step help for creating IDoc to IDoc data transfer through ALE.
My scenarion is like the following:
there will be two client in two R/3 system..(Sending and receiving)....
in sending system i want to insert data in a particular table....
that data will be automatically updated in receiving system..
plz help meeeeeeee
thanks...
points will be rewarded.......

Hi Soumya,
Follow the process as below
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards,
Satish

How to extend Generated Idoc - HRCC1DNINORD01?

Hi Gurus,
I have a requirement add two custom fields to the Standard IDOC HRCC1DNINORD01. For this i am using IDOC Extension but system through Error like Extension is not possible for Generated IDOCs. So my self find that we cannot Enhance the Generated IDOCs,instead of that Enhance the BAPI by using BDBG Transaction. But i don't understand this BDBG Transaction corresponding Object Type, Method. Please guide me to full fill my requirement.
Thanks in advance.
Regards,
SR Krishna.

Hi,
Actually, BDBG is a transaction to be created the new custom idoc types and message types all those stuff.
BDBG transaction will create the automatically custom idoc type and message type.
As per your requirement, You would create the custom idoc type and accordingly you have configure in the Partner profile.
Because one of the scenario, my case CRESTA01 needs the extension but it is not possible to create the extension for that. So, We have checked with BDBG but, finally we have checked and seen that internally, It has to be creating custom idoc type and message.
Manually, you have to create the custom idoc type with contains to your structure.
I hope you understand the scenario.
Thanks,
Chandra

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

The application, C:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe, generated an application error The error occurred on 10/01/2009 @ 11:31:59.964 The exception generated was c0000005 at address 7C81BD02 (ntdll!ExpInterlockedPopEntrySListFault)

Hi,
I get this error randomly when i run my VB 6.0 application which calls Photoshop CS2 actions. I went through many forums, but could not manage to get the right solution for this.
"The application, C:\Program Files\Adobe\Adobe Photoshop CS2\Photoshop.exe, generated an application error The error occurred on 10/01/2009 @ 11:31:59.964 The exception generated was c0000005 at address 7C81BD02 (ntdll!ExpInterlockedPopEntrySListFault)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
OS: WIndows Server 2003 SP2
Photoshop CS2
ANy help on this will be highly appreciated.
Thanks in advance,
Smiley

I see this sort of error notice in Bridge and Photoshop, preceded by the message " Photoshop (or Bridge) has encountered a problem and must close. Tell MS.
Yes or No."
It most frequently happens in PS when running Dfine 2.0. I have no clue what triggers the Bridge closure. It happens randomly.
CS3, so nobody gives a tinkers dam, I suppose.
I see this kind of message in software testing on a regular basis. Of course, when the test is under way, the software is generating a detailed log file which we package up as part of a bug report. Then at the bug scrubs, lively discussions ensue as to who has to fix what!
I can only image what would happen if the Dfine people and the PS people had to sit through one of those!

Creation of IDOC through abap program.

hello all,
I hav created idoc through abap program. I hav used FM 'Master_idoc _distrribute'.this program creates an idoc but giving status 30. can any one tell me how to get status 03. I hav already created port, Logical sys,partner no.,distribution model.
My Program is as follows:
ABLES : CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control Record
 ORDER_NO TYPE CRMT_OBJECT_ID VALUE '5000000032'," SEGMENT ORDER DATA
 PRODUCT TYPE CRMT_ORDERED_PROD VALUE 'SRV_01',
 QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
DATA : ZORDER LIKE ZORDER_NUM OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE. "Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZORDER_NUM'.
PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZORDER_IDOC2', "Message Type
 C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS', "Partner type of receiver
 C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'BSNL_OUT',
 C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000006',
 C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'SAPBCD0000',
 C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'BCDCLNT100',
 C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZORDER2',
 C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'. "Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*& Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = C_MESTYP. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
APPEND S_CTRL_REC.
ENDFORM. " generate_control_record
*& Form send_idoc
FORM SEND_IDOC.
ZORDER-ORDER_NO = ORDER_NO.
ZORDER-PRODUCT = PRODUCT.
ZORDER-QUANTITY = QUANTITY.
APPEND ZORDER.
T_EDIDD-SEGNAM = C_ZRZSEG1.
T_EDIDD-SDATA = ZORDER.
APPEND T_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
 EXPORTING
 MASTER_IDOC_CONTROL = S_CTRL_REC
 TABLES
 COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
 MASTER_IDOC_DATA = T_EDIDD
 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.
 COMMIT WORK.
 LOOP AT T_COMM_IDOC.
 WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
 ENDLOOP.
ENDIF.
ENDFORM. " send_idoc
I hav created segment , basic type,message typealso and release also .I also linked them.
Plz help me.
Hemlata

Hi Hemalatha,
Just call this Progream RSEOUT00 from your Zprogram and pass the basic parameters like IDOC number, Basic type,Partner number etc.
You can check the parameters by executing the Program RSEOUT00.
This Program will change the status of your IDOC 30 to 03.
Thanks.
Note:Reward Points if you find useful.

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.

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.

File to idoc - IDX5 Error

Hi,
I am doing file to idoc scenario. I have done all required configuration in IR and ID. This Scenario is now executing properly and in SXMB_Moni it is also showing new generated IDOC number.
But when I tried to locate same IDOC in R/3 system i am not able to locate it. In IDX5 tcode is showing error msg like "No authorization to send IDocs with message type ZTESTMSG".
Please guide me on this.
Thanks,
Sunil

Hi Sunil,
Please can you check the RFC in IDX1 (RFC destination given in PORT)which is used for sending the IDOC.
Does it have all the authorizations.
Also you can try this using xiappluser in the RFC destination.
Regards
Vijaya

Generate IDOC through error

Similar Messages

Maybe you are looking for