Regarding errpr idoc reprocess
Hi Experts,
Currently iam working on inbound idoc 'ORDERS04'.
For background process we have the sap standard program 'RBDAPP01'.
how can i achive the following requirement.i have created one custom table for this req with idoc number,PO number and Status.
Check on the table to see idoc program is running
If idoc program is running, exit
Else set the table and call the idoc program to process new and re-process error idocs
When the idoc program is done and control is back to the control program, clear the status in the table and exit
Rgds,
Krishna.
Hi Balakrishna,
All the inbound Idocs will be updated in the tables EDIDC,EDID4,EDIDS at first.
So, create internal table for any of the above tables and dont forget to select the fields time and date.
Capture all the Idocs created at that time. Now, for these Idocs you need to check whether the
background job has processed them or not. Is that correct?
So, to check whether the background job which runs RBDAPP01 program is running or not you can do manipulations on the table TBTCO. This table will have the status whether the job is running or not.
If not, you can schedule a job by inserting an entry in the table TBTCS or you can also call the job by using JOB_OPEN FM
Hope you got the clue how to do that. I think you can avoid the custom table to achieve this.
Thanks,
Babu Kilari
Similar Messages
-
Hi,
I have a problem with idoc reprocessing .An idoc contains the date field which shows the system date.I t always shows the default system date as Thursday.
But when we reprocess some idocs ...they are not showing the default system date (Thurs day) showing the current date .
Pls advice.
Regards,
Somenathhi
use
report RBDAPP01
to change status from 51(application document not posted)
to 53(application document posted)
reward for use ful points
regards
Nagesh.Paruchuri -
Regarding ALE/Idocs PDFs & complete Documentation & Step by Step Procedure
Hi Gurus,
Iam working on Netweaver XI and i need some PDF's on ALE/Idocs.
1. How to create and send a custom idoc?
2. Serialization of idocs?
3. Archiving of idocs?
4. Idoc Acknowledgement?
5. How to send multiple Idocs at a time?
6. Idoc Sheduling?
7. Idoc bundling and Packaging?
8. How to Debug a Idoc?
For the above questions i need complete procedure and Pdf's upon these and send me some FAQ's on them.can any one send me the details plz very urgent.plz send Especially pdf's. My id is ajaykodali22 at the rate of gmail.com
Thanks & Regards,
ajay kodali.Hi,
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards,
Shiva. -
Hi....
Please send some FAQ'S regarding ale,idocs
thanks
k..swaminathHi,
plz go through the links...
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
Reward points if u find useful.
Regards,
Nagaraj -
I have developed a File to IDOC interface in PI/XI. The file I pick up will contain a list of invoices from a vendor system ,
that I convert into ACLPAY IDOCs and post invoices.
When the IDOCs are posted into our SAP system some of the IDOCs fail and some of them are successful.
At the end of a business day the user will execute txn we05 to see the status of the IDOCs that came in for that day.
If any of the IDOCs failed the user would use WE19 to correct the data and reprocess the IDOC again.
The problem is the old IDOC that came in still has a error status and the new IDOC created by modifying the old IDOC doesnu2019t have any reference to the older IDOC.
Is there a way to see if and IDOC was created by reprocessing an already existing IDOC?
Or is there a better method to handle my scenario?
Thanks
SivaHi siva,
there are different programs and t-codes available to reprocess the error Idocs
with out creating new idocs.
Program RBDMANI2 for status 51 & 52
Program RBDAPP01 for status 64 ,66
Program RBDAGAIE for status 32 and 69 (Edited IDocs)
Program RBDSYNER for status 26
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC - Creating IDoc Type from Change Pointers
RSEOUT00 - Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Program RSEOUT00 for status 30
re-process IDocs failing in 29 status, use program RBDAGAIN.
transactions WEINBQUEUE and WEOUTQUEUE to control the individual queues
Prabhudas -
IDOC reprocessing with new conversion rules
Hi All,
we've created IDOCs and after the creation the conversion rules are changed. Now we want to reprocess the IDOC's and in the reprocessing we want to use the new conversion rules.
I've tried just reprocessing, I also tried WE19, but with these 2 the conversion rules seem to left untouched.
Has anyone a solution were I can reprocess making use of the new rules?
kind regards,
PieterHi,
I've debugged the reprocessing of the idoc and it seems indeed I had to change the status, however not all statusses result in reprocessing of the rules. Status '29' Error in ALE Service works. So my problem is solved.
Thank you.
kind regards,
Pieter -
Outbound error IDoc reprocessing
I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
1. In general scenario how do we handle outbound error idocs?
2. Is system process codes are used only for notifications or error processing?
Inputs will be appreciated regd outbound error reprocessing .
Thanks.Hi Indira,
1. In general scenario how do we handle outbound error idocs?
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
2. Is system process codes are used only for notifications or error processing?
The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
Hoep this will help.
Regards,
Ferry Lianto -
hello
i need to reprocess idocs in status 03 through bd87
but it is not allowing
please helpHi Manu,
Looks like you are trying to reprocess the IDOC which is already processed correctly.
Unfortunately there is no way by which you can do it.
I can give you a work around though:
1) Go to WE19 enter your IDOC number which already has status 03 and execute.
2) On next screen it will display the IDOC, choose approporate button on toolbar (standard Function Module) to process it.
3) This will generate the new IDOC similar to the one which was posted completely.
4) Now the new IDOC should have status ready (Unless you have clicked Process Immediately in WE21 for this message type, it shud be execute by Background Job).
This approch is applicable for testing.
Let me know if it solves your query.
Regards
Shital -
RBDMANI2 Idoc Reprocessing IDOC Failure Notification
Hi SAP Friends,
I developed an inbound interface for LIV electronic invoice(MIRO) with basic type INVOIC02. At present everything going smooth.
i scheduled a background job with the program RBDMANI2 to reprocess the failed IDOCS. i.e if any failed idocs required SAP side changes, users will complete the changes. Then the scheduled job will process the failed IDOC.
IDOC will process if corrected data is satisfying else IDOC will fail again with Status 51.
Now the failed IDOC notification we are not getting any notfication.
If IDOC is failing first time idoc failure notification will come. At that point Object Type IDOCINVOIC & Event INPUTERROROCCURREDMM is triggering.
When i am reprocessing through the scheduled job of program RBDMANI2 , i am not getting any failed notification.
Can anyone help me out where i am missing the event. i need to activate any other event linkage for the reprocessing.
I tried with SWELS, i did not get any event when i execting the program RBDMANI2.
Appreciate your help and valuable inputs.
Thanks & Regards,
Srinivas BhavanamSrinivas, per my understanding the failure event is only triggered once. You can attest this yourself by executing the associated workflow. If you select the process option and all errors were not addressed, the current work item remains active ; eventually the error message will be changed in case the IDOC is now failing for another reason. There is only one workflow instance for the same IDOC ; the failed batch processing does not generate any new workflow or IDOCs, it only updates the current instances (workflow) and add an entry to the IDOC status table (EDIDS)
-
Hi Gurus,
I have a problem wiht IDOCs. One of my End User is reporcessing IDOC of other country. When I look into his authorizations, he don't have authorization for that particular country where he is reprocessing. Even when I asked user, he don't know what exactly going on, but in reports system is howing user id.
If any one have any idea how it is allowing user to repocess pl let me know.
Regards
Jayakar ReddyBD87 - is used to reprocess the Idocs.
-
Regarding Exit/IDOC Related TD
Hi,
Can anybody tell me what is the code required to be written folowing TD points.
Before below TD i have populated one internal table in
userexit_save_document exit and submitted following new program need to be written as below:
SUBMIT gv_prog
WITH SELECTION-TABLE t_seltab
VIA JOB gv_jobname NUMBER gv_jobnum "USER puser
AND RETURN TO SAP-SPOOL
SPOOL PARAMETERS gv_params
WITHOUT SPOOL DYNPRO.
As i am new to IDOC Concept can anybody help to write following code!
Create new custom program that will create the CTO deletion idocs to send to WWCLASS
Requirements:
o Need to be able to import data in from the save_doc userexit and create and post the idoc
 Import needed data from userexit_save_document
 Fill the control record to send into function (waiting for FA to get this information to me, as they have not yet created the partner)
DOCTYP =
OUTMOD = 2
SERIAL = sy-datum
SERIAL+8 = sy-uzeit
IDOCTP = ORDERS05
MESTYP = ORDERS
MESCOD = ??????
RCVPRT = ??????
RCVPRN = ??????
RCVPFC = ??????
RCVPOR = ??????
 Fill the E1EDK01 segment (Header level segment)
CURCY = currency
ZTERM = zterm
BELNR = order number (vbeln)
 Fill the E1EDP01 segment (Item level segment)
POSEX = item number (posnr)
ACTION = 001
 Fill the E1EDP19 segment (Item Object Identification segment)
QUALF = OID to represent old GCTO id
IDTNR = GCTO ID from vbap
 Generate the idoc
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
MASTER_IDOC_CONTROL = cntrl data
TABLES
COMMUNICATION_IDOC_CONTROL = cntrl data(returned)
MASTER_IDOC_DATA = idoc data
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5
Based on the documentation for this standard function, you will need to do a commit work after calling the program in order to ensure the idoc is dispatched.
o Need to be able to capture failures and send report to users in e-mail
 Failures fall into 2 categories:
An IDOC was created, but the posting fails with error status. In this case, we still want to capture this in the file as a failure, but the users should re-process this with standard SAP transactions (can find status of created idoc in the returned communication_idoc_control table).
An IDOC was NOT created for some reason. In this case, we will need to capture all the necessary information needed to try and re-create an idoc
 File should be sent via e-mail to users defined in a table.
Use standard FM SO_NEW_DOCUMENT_SEND_API1 to send document to specified users
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
document_data =
document_type = 'RAW'
put_in_outbox = ''
TABLES
object_content =
receivers =
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
OTHERS = 8.
Document Data should include the email header information. Something that denotes to user that this is an WWCLASS CTO Deletion IDOC Error Report
Object Content should include the following information:
o IDOC# (in cases where the idoc was created, but has fail status)
o Order Number
o Currency
o Terms of Payment
o Item Number
o GCTO ID
Receivers should be the list of addresses that will receive the email.
o Read table ZCMAIL with REPID = this program name, and MAIL_LIST = to retrieve all the addresses that will need to have the report sent. Will need to send the FA the name of this program so they can setup the table entries properly.
o Need to add parameters to program that will also allow the user to run this program manually so they can re-create the idoc in cases where the idoc was erroneously not created in normal process.
 Allow user to enter a file name that could be uploaded from their hard drive that will contain all data need to create the idoc.
 Generate the idoc based on data in file.
 File could look similar to the data reported in the error report
Can anybody help me in writing code for above TD!
Thanks in advance.
Thanks & Regards,
Deep.HI,
Any solutions for the same!
Thnaks,
Deep. -
Regarding Inbound Idoc creation
Hi,
I am trying to create a Idoc from a xml file without using XI.
I can read the details from the file and populate a internal table.
I am not clear when the IDoc number will be generated.
Can any one gtel me which FM actually starts the inbound proces?
Which FM will generate the IDOC no for the incoming Idoc ?
I am not clear as to which function module i should pass my internal table with data to create a IDoc.
Please help
Regards,
VigneshHi,
try MASTER_IDOC_DISTRIBUTE function module for create idoc.
rgds
shibu -
Regarding Custom IDOC Creation
Hi All,
I Am New to ABAP , Any one Please Give me the Step -By Step Procedure to create Custom IDOC.
I Have this Link with me.
Step by step custom IDOC creation
But I Don't Know that What should i Give field names and Data elements
How to create Field names And Data elements
Regards
VamsiHi,
U need a custom IDOC when the elements in the standard IDOC is not there according to requirement. ex. in IDOC cremas04 u want the Country code should be there.
Then U go for custom iDOC and create a Y/Z i.e custom idoc and add one structure and add the required fiellds.
Check this link for Step by Step guide
http://www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
CHeck this link for a IDOC ...The steps are mentioned in details about creating custom idoc..
http://www.allsaplinks.com/idocbasicsunderstanding.html
http://www.allsaplinks.com/idoc.html
http://www.allsaplinks.com/idoc_sample.html
Please check this link.
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards -
Regarding "WPUFIB01"idoc enhancement
hi ,
i have a std idoc "WPUFIB01" to which i am trying to add two new fields with the use of E1WXX01 cutomised segment.all the process is done using inbound processing.Currently i am using the enhancement name "WPUE0002" and the user exit i am using is "EXIT_SAPLWPUE_130".my problem is that i that i am unable to read the segment "E1WXX01" while processing the idoc.pls help ...thanx in advance..Hi Rahul,
Did you release the segment and the Custom IDOC TYPE.
Check whether you are using the correct idoc type.
Check if the segment is populated in the idoc.
Regards
Arun -
Idoc reprocessing in Custom program
I have a custom program which displays the IDoc data for the message type = ZSTLSP in the ALV format.
Requiremt is that I shall select a record and change one of the coulmn contents . A button 'Reprocess' will be
made available , when clicked it needs to reprocess the Idoc . The reprocessed idoc will be strored with the new values entered
and the original idoc will be stored with status 70.
Kindly let me know how to reporcess the IDoc in the custom program.
p.s.: Function module IDOC_INPUT does also reprocess ..but it does not disoplays the updated status.Hello,
You may call standard program RBDAPP01 to reprocess the IDOCs using SUBMIT statement. Pass the IDOC Number, Message type etc. while submitting the program.
Thanks,
Venu
Maybe you are looking for
-
Hi all, I'm having a problem with exporting a workbook into an excel sheet. The problem is that NOTHING HAPPEND. I realy don't know what is going on. For the same account I tried to export another report... and every thing was ok (the only thing that
-
How to reverse the wrognly posted cash journal document
-
How to come to know the number of downloads your app has got?
I have just developed an app and want to know how many people have downloaded it.. I tried to go on statistics but that wasn't helpful
-
Are there any one ever upload the file to CIC0 for transaction creatation
Dear Sir, Our server is CRM 5.0 , I would like to upload the data to create transaction in CIC0 . Do you ever use the bapi : BAPI_ACTIVITYCRM_CREATEMULTI ? Is is work or not? Thank you and best regards, Vimol
-
After updating my ATV to 6.1.1 no airplay from iPhone or iPad
This happens every time I update my ATV 2 to new software. No airplay from iPad 1 or iPhone 4 ( running ios 7.1.1 ) - this time after ATV update to version 6.1.1 Tried everything : resetting ATV, disconnecting cables, resetting router, turning netw